-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make this example actually run 🏃 #3079
Conversation
The examples should at the least contain Runs that execute them (and even better, should include an assertion that verifies they did what was expected) otherwise all that is being verified is that the spec is valid.
/kind cleanup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two small fixes if you feel like it when you're here. Lgtm anyway since it's not really related to your change.
- name: print-date-human-readable | ||
image: bash:latest | ||
script: | | ||
#!/usr/bin/env bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't actually need the shebang here since it's script mode.
- name: print-date-unix-timestamp | ||
image: bash:latest | ||
script: | | ||
#!/usr/bin/env bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dlorenc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm 🙏 thankyou this always surprises me! |
/test check-pr-has-kind-label |
Changes
The examples should at the least contain Runs that execute them (and
even better, should include an assertion that verifies they did what was
expected) otherwise all that is being verified is that the spec is
valid.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes